<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>SystemComponent</title>
		<link type="text/css" rel="stylesheet" href="PLUGINS_ROOT/org.polarsys.capella.doc/html/styles.css"/>
	</head>
	<body>
		<h1 id="System_.2F_Actor">System / Actor</h1>
		<p>This wizard helps you setting the properties of a System Component (System or Actor).</p>
		<p>
			<b>Base </b>
		</p>
		<table border="1">
			<tr>
				<td>
					<p>
						<b>Field</b>
					</p>
				</td>
				<td>
					<p>
						<b>Description</b>
					</p>
				</td>
				<td>
					<p>
						<b>Default</b>
					</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Name</b>
					</p>
				</td>
				<td>
					<p>The name of the current Element.</p>
				</td>
				<td>
					<p>&lt;generic name&gt;</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Summary</b>
					</p>
				</td>
				<td>
					<p>A short headline about the role of the current Element.</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>isAbstract</b>
					</p>
				</td>
				<td>
					<p>Specifies whether the current Actor is abstract or not. An abstract Actor is an Actor that is expected to be specialized by one or several concrete Actors.</p>
					<p>
						<i>Note 1: At this stage in the tool, the &quot;isAbstract&quot; feature is not exploited (no specific constraint, no associated validation rules, etc.).
							<br/> Note 2: Unless having a good reason to do so, &quot;isAbstract&quot; feature shall not be used when strictly following the Arcadia methodology.
						</i>
					</p>
				</td>
				<td></td>
			</tr>
			<tr>
				<td>
					<p>
						<b>isHuman</b>
					</p>
				</td>
				<td>
					<p>Specifies whether the current Actor is human or not.</p>
				</td>
				<td></td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Super</b>
					</p>
				</td>
				<td>
					<p>One or several System Actors from which the current Actor is a specialization.</p>
					<p>
						<i>Note 1: At this stage in the tool inheritance relationships between Actors are not fully exploited. 
							<br/> Note 2: Unless having a good reason to do so, inheritance shall not be used when strictly following the Arcadia methodology.
						</i>
					</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Implemented</b>
						<b> Interfaces</b>
					</p>
				</td>
				<td>
					<p>The list of Interfaces directly implemented (i.e. not through Component Ports) by the current Actor. Interfaces aggregate Exchange items (Operations, Events, Flows, Shared Data).</p>
					<p>
						<i>Note: Unless having a good reason to do so, Implemented Interfaces shall not be used when strictly following the Arcadia methodology.</i>
					</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Used</b>
						<b> Interfaces</b>
					</p>
				</td>
				<td>
					<p>The list of Interfaces directly use (i.e. not through Component Ports) by the current Actor. Interfaces aggregate Exchange items (Operations, Events, Flows, Shared Data).</p>
					<p>
						<i>Note: Unless having a good reason to do so, Used Interfaces shall not be used when strictly following the Arcadia methodology.</i>
					</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Allocated</b>
						<b> Functions</b>
					</p>
				</td>
				<td>
					<p>The list of System Functions performed by the current Actor.</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Realized</b>
						<b> Operational Entities</b>
					</p>
				</td>
				<td>
					<p>One or several Operational Entities from which the current System Actor is a refinement.</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
		</table>
		<p>
			<b>Description</b>
		</p>
		<p>This field contains the business description of the current element. Links towards other model elements or diagrams can be created in this description using the &quot;Add Link&quot; button.</p>
		<p>By default this field in read-only, so that hyperlinks can be navigated. To start editing the description, click first on the &quot;Edit&quot; button at the very left side of the toolbar.</p>
		<p>
			<b>Extensions</b>
		</p>
		<table border="1">
			<tr>
				<td>
					<p>
						<b>Field</b>
					</p>
				</td>
				<td>
					<p>
						<b>Description</b>
					</p>
				</td>
				<td>
					<p>
						<b>Default</b>
					</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Applied</b>
						<b> Property Values</b>
					</p>
				</td>
				<td>
					<p>One or several Property Values related to the current Element. These Property Values might be located right under the current Element or anywhere else in the Model.</p>
					<p>The &quot;browse&quot; button allows associating an already existing Property Value (not necessarily located under the current Element). The «cross» button allows removing the association between the selected Property Value and the current Element. This action does not delete the Property Value itself.</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Applied</b>
						<b> Property Value Group</b>
					</p>
				</td>
				<td>
					<p>One or several Property Value Groups related to the current Element. These Property Values Group and the Property Values they contain might be located right under the current Element or anywhere else in the Model.</p>
					<p>The &quot;browse&quot; button allows associating an already existing Property Group (not necessarily located under the current Element). The «cross» button allows removing the association between the selected Property Value and the current Element. This action does not delete the Property Value itself.</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
		</table>
		<p>
			<b>Management</b>
		</p>
		<table border="1">
			<tr>
				<td>
					<p>
						<b>Field</b>
					</p>
				</td>
				<td>
					<p>
						<b>Description</b>
					</p>
				</td>
				<td>
					<p>
						<b>Default</b>
					</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Visible in Documentation</b>
					</p>
				</td>
				<td>
					<p>Specifies whether this element is exposed to the Documentation Generation tool.</p>
				</td>
				<td>
					<p>True</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Visible in Link Manager</b>
					</p>
				</td>
				<td>
					<p>Specifies whether the current element is exposed to the Link Manager tool, for example for traceability with Requirements.</p>
				</td>
				<td>
					<p>True</p>
				</td>
			</tr>
			<tr>
				<td>
					<p>
						<b>Progress Status</b>
					</p>
				</td>
				<td>
					<p>Not all elements in the design phase of a System have the same maturity (some are Drafts, some need to be reviewed, etc.). This field allows setting the maturity level of the current Element.</p>
				</td>
				<td>
					<p>&lt;blank&gt;</p>
				</td>
			</tr>
		</table>
	</body>
</html>